Systems and Methods for Providing a Tagging Interface for External Content

ABSTRACT

Computer-implemented systems and methods are disclosed for providing a tagging interface for tagging external content. In accordance with some embodiments, a method is provided for tagging content external to a database system. The method comprises accessing the external content via a web browser of an electronic device. The method also comprises enhancing the web browser by providing a tagging interface for tagging at least a portion of the external content. The method further comprises receiving created tag associated with a tagged portion of the external document content, and exporting the external content and the received tag to the database system. The tagging interface can also provide an option to export the created tag to an internal database system.

REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of priority to U.S. Provisional Patent Application 61/801,556, filed on Mar. 15, 2013, the disclosure of which is expressly incorporated herein by reference in its entirety.

BACKGROUND

Data is commonly stored in computer-based systems in fixed, rigidly structured data stores. For example, one common type of data store is a “flat” file such as a spreadsheet, plain-text document, or XML document. Another common type of data store is a relational database comprising one or more tables. Other examples of data stores that comprise structured data include, without limitation, files systems, object collections, record collections, arrays, hierarchical trees, linked lists, stacks, and combinations thereof.

Often, the underlying structure of these types of data stores is poorly suited for data analysis. One approach for facilitating a more efficient analysis of data in such data stores is to reorganize that data according to an object model that defines object structures and relationships between the object structures. Tagging is a method used to create objects, properties, or links between objects and/or properties in structured or unstructured data. It can add structure to unstructured data or add further structure to structured data.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings showing example embodiments of the present application, and in which:

FIG. 1 is an block diagram depicting an exemplary internal database system, consistent with embodiments of the present disclosure.

FIGS. 2A and 2B are screenshots depicting an exemplary interface for tagging an unstructured document stored in the database system of FIG. 1, consistent with embodiments of the present disclosure.

FIG. 3 is a block diagram depicting an exemplary system comprising the database system of FIG. 1 and one or more components external to the database system of FIG. 1, consistent with embodiments of the present disclosure.

FIG. 4 is a screenshot depicting an exemplary tagging interface via a web browser displaying an external content, consistent with embodiments of the present disclosure.

FIG. 5 is a flowchart representing an exemplary method for tagging external content, consistent with embodiments of the present disclosure.

FIG. 6 is block diagram of an exemplary computer system with which embodiments described herein can be implemented, consistent with embodiments of the present disclosure.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Reference will now be made in detail to the embodiments, the examples of which are illustrated in the accompanying drawings. Whenever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

FIG. 1 shows, in block diagram form, an exemplary data fusion system 100, consistent with embodiments of the present disclosure. Among other things, system 100 facilitates transformation of one or more data sources, such as data sources 130, into an object model 160, whose semantics are defined by an ontology 150. The transformation can be performed for a variety of reasons. For example, a database administrator can wish to import data from data sources 130 into a database 170 for persistently storing object model 160. As another example, a data presentation component (not depicted) can transform input data from data sources 130 “on the fly” into object model 160. Object model 160 can then be utilized, in conjunction with ontology 150, for analysis through graphs and/or other data visualization techniques.

System 100 comprises a definition component 110 and a translation component 120, both implemented by one or more processors on one or more computing devices executing hardware and/or software-based logic for providing various functionality described herein. As will be appreciated from the present disclosure, system 100 can comprise fewer or additional components that provide various functionalities described herein. Such components are, for clarity, omitted from FIG. 1. Moreover, the component(s) of system 100 responsible for providing various functionalities can further vary from embodiment to embodiment.

Definition component 110 generates and/or modifies ontology 150 and a schema map 140. Exemplary embodiments for defining an ontology (such as ontology 150) is described in U.S. Pat. No. 7,962,495 (the '495 patent), issued Jun. 14, 2011, the entire contents of which are expressly incorporated herein by reference for all purposes. Among other things, the '495 patent describes embodiments that define a dynamic ontology for use in creating data in a database. For creating a database ontology, one or more object types are created where each object type can include one or more properties. The attributes of object types or property types of the ontology can be edited or modified at any time. And for each property type, at least one parser definition is created. The attributes of a parser definition can be edited or modified at any time.

In some embodiments, each property type is declared to be representative of one or more object types. A property type is representative of an object type when the property type is intuitively associated with the object type. For example, a property type of “Social Security Number” may be representative of an object type “Person” but not representative of an object type “Business.”

In some embodiments, each property type has one or more components and a base type. In some embodiments, a property type may comprise a string, a date, a number, or a composite type consisting of two or more string, date, or number elements. Thus, property types are extensible and can represent complex data structures. Further, a parser definition can reference a component of a complex property type as a unit or token.

An example of a property having multiple components is a Name property having a Last Name component and a First Name component. An example of raw input data is “Smith, Jane.” An example parser definition specifies an association of imported input data to object property components as follows: {LAST_NAME}, {FIRST_NAME}→Name:Last, Name:First. In some embodiments, the association {LAST_NAME}, {FIRST_NAME} is defined in a parser definition using regular expression symbology. The association {LAST_NAME}, {FIRST_NAME} indicates that a last name string followed by a first name string comprises valid input data for a property of type Name. In contrast, input data of “Smith Jane” would not be valid for the specified parser definition, but a user could create a second parser definition that does match input data of “Smith Jane.” The definition Name:Last, Name:First specifies that matching input data values map to components named “Last” and “First” of the Name property.

As a result, parsing the input data using the parser definition results in assigning the value “Smith” to the Name:Last component of the Name property, and the value “Jane” to the Name:First component of the Name property.

Referring back to FIG. 1, schema map 140 can define how various elements of schemas 135 for data sources 130 map to various elements of ontology 150. Definition component 110 receives, calculates, extracts, or otherwise identifies schemas 135 for data sources 130. Schemas 135 define the structure of data sources 130—for example, the names and other characteristics of tables, files, columns, fields, properties, and so forth. Definition component 110 furthermore optionally identifies sample data 136 from data sources 130. Definition component 110 can further identify object type, relationship, and property definitions from ontology 150, if any already exist. Definition component 110 can further identify pre-existing mappings from schema map 140, if such mappings exist.

Based on the identified information, definition component 110 can generate a graphical interface 115. Graphical interface 115 can be presented to users of a computing device via any suitable output mechanism (e.g., a display screen, an image projection, etc.), and can further accept input from users of the computing device via any suitable input mechanism (e.g., a keyboard, a mouse, a touch screen interface). Graphical interface 115 features a visual workspace that visually depicts representations of the elements of ontology 150 for which mappings are defined in schema map 140. Graphical interface 115 also includes controls for adding new elements to schema map 140 and/or ontology 150, including objects, properties of objects, and relationships, via the visual workspace. After elements of ontology 150 are represented in the visual workspace, graphical interface 115 can further provide controls in association with the representations that allow for modifying the elements of ontology 150 and identifying how the elements of ontology 150 correspond to elements of schemas 135. Optionally, the graphical interface 115 can further utilize the sample data 136 to provide the user with a preview of object model 160 as the user defines schema map 140. In response to the input via the various controls of graphical interface 115, definition component 110 can generate and/or modify ontology 150 and schema map 140.

In some embodiments, graphical user 115 can provide an interface providing a user with the ability to add structure to an unstructured document stored in data sources 130 by tagging one or more portions (e.g., text) within the document. Defining tags and applying these tags to a portion of the document can create object, properties, or links creating a relationship between one or more objects and/or properties. An exemplary interface, including related features and pop-up windows, is described below with reference to FIGS. 2A and 2B.

FIG. 2A is a screenshot depicting an exemplary interface 200 for tagging an unstructured document stored in the database system of FIG. 1. As shown in FIG. 2A, interface 200 can display a document that was unstructured before tag 210 had been applied. To tag text in the document, a user can for example select text (in this case, “Olympics”) and right-click on a mouse for a pop-up 220 to appear and to provide the user with the ability to select an “Add Tag . . . ” option.

Selecting the “Add Tag . . . ” option can result in, for example, a “Tag as . . . ” pop-up window appearing, an example of which is shown in FIG. 2B. Pop-up window 230 provides the user with the ability to assign selected text (in this case, “Dave McGovern”) to a person object and/or a name property.

Referring back to FIG. 1, transformation component 120 can be invoked after schema map 140 and ontology 150 have been defined or redefined. Transformation component 120 identifies schema map 140 and ontology 150. Transformation component 120 further reads data sources 130 and identifies schemas 135 for data sources 130. For each element of ontology 150 described in schema map 140, transformation component 120 iterates through some or all of the data items of data sources 130, generating elements of object model 160 in the manner specified by schema map 140. In some embodiments, transformation component 120 can store a representation of each generated element of object model 160 in a database 170. In some embodiments, transformation component 120 is further configured to synchronize changes in object model 160 back to data sources 130.

Data sources 130 can be one or more sources of data, including, without limitation, spreadsheet files, databases, email folders, document collections, media collections, contact directories, and so forth. Data sources 130 can include structured data (e.g., a database, a .csv file, or any tab delimited or fixed-width file), semi-structured data (e.g., an email, an email server, or forms such as a suspicious activity report or currency transaction report), or unstructured data (e.g., encoded files such as PDF, sound, and image files). Data sources 130 can include data structures stored persistently in non-volatile memory. Data sources 130 can also or instead include temporary data structures generated from underlying data sources via data extraction components, such as a result set returned from a database server executing an database query.

Schema map 140, ontology 150, and schemas 135 can be stored in any suitable data structures, such as XML files, database tables, and so forth. In some embodiments, ontology 150 is maintained persistently. Schema map 140 can or cannot be maintained persistently, depending on whether the transformation process is perpetual or a one-time event. Schemas 135 need not be maintained in persistent memory, but can be cached for optimization.

Object model 160 comprises collections of elements such as typed objects, properties, and relationships. The collections can be structured in any suitable manner. In some embodiments, a database 170 stores the elements of object model 160, or representations thereof. In some embodiments, the elements of object model 160 are stored within database 170 in a different underlying format, such as in a series of object, property, and relationship tables in a relational database.

FIG. 3 is a block diagram depicting an exemplary system 300 comprising database system of FIG. 1 and one or more components external to the database system of FIG. 1. System 300 comprises database system 100, which is referred to as an “internal system,” and one or more components located external to database system 100. These external components can include, for example, electronic device 310, network 320, and server 330.

Electronic device 310 can provide the ability to communicate with server 330 via network 320. By way of example, electronic device 310 can be a personal computer, a tablet computer, a personal digital assistant (PDA), a mobile phone, a smart-phone, or any other web-enabled computing device with a processor and a memory. Electronic device 310 can provide support for software applications including, a web browser (or other network communication software), that can also comprise a special add-on, a plug-in, or a bookmarklet. In some embodiments, electronic device 310 and a portion of network 320 can be included in internal database system 100. For example, electronic device 310 could provide graphical interface 115 of internal database system 100.

Electronic device 310 can also include, for example, one or more processors (not shown), a memory device (not shown), and a data interface (not shown). The one or more processors can be a single or multiple microprocessors, field programmable gate arrays (FPGAs), or digital signal processors (DSPs) capable of executing particular sets of instructions. Computer-readable instructions can be stored on a tangible non-transitory computer-readable medium, such as a flexible disk, a hard disk, a CD-ROM (compact disk-read only memory), and MO (magneto-optical), a DVD-ROM (digital versatile disk-read only memory), a DVD RAM (digital versatile disk-random access memory), or a semiconductor memory. Alternatively, the instructions can be implemented in hardware components or combinations of hardware and software such as, for example, Application Specific Integrated Circuits (ASICs), special purpose computers, or general purpose computers.

Server 330 can comprise hardware, software, or a combination of both that provides the capability for communicating with electronic device 310 via network 320. Server 330 provides content to electronic device 310. This content is stored external to database system and can be referred to as “external content.” External content can include a web page, a document, a PDF file, a sound or audio file, an image or video file, a database, an email, a form, etc. In some embodiments, server 330 can be a part of a network cloud, which can include, for example, one or more networked servers.

Network 320 can be, for example, the Internet, an intranet, a local area network, a wide area network, a campus area network, a metropolitan area network, an extranet, a private extranet, any set of two or more coupled electronic devices, or a combination of any of these or other appropriate networks. In the exemplary embodiment of FIG. 3, network 320 is considered external to database system 100, but portions of network 320 (as stated above) can be located in internal database system 100.

FIG. 4 is a screenshot 400 depicting an exemplary tagging interface via a web browser that can display external content. For purposes of illustration, screenshot 400 depicts a news web page on a web site (e.g., BBC™ web site) displaying external content 460 on a web browser of an electronic device (e.g., electronic device 310). Screenshot 400 also depicts tagging interface 450. In some embodiments, tagging interface 450 can be displayed in response to a user installing and activating a bookmarklet in the web browser. In other embodiments, tagging interface 450 can be displayed in response to a user installing and activating a plug-in in the web browser. In some embodiments, a user may login to internal database system 100 before the bookmarklet or plugin is activated.

Tagging interface 450 can be used to create tags associated with at least a portion of external content 460. In some embodiments, the user can select at least a portion of external content 460. For example, if external content 460 is text-based, the user can select at least a portion of the text of external content 460. In other embodiments, if external content is an image or video, the user can select at least a portion of the image or at least a frame of the video to create one or more tags associated with the selected portions of external content 460. It can be understood that there can be other types of external content 460 that can also be selected for creating tags. For example, an audio file having a voice of a person can be tagged as a property of a person object.

When the user selects a portion of external content 460, at least some of the fields of tagging interface 450 (e.g., TITLE 412, TYPE 410, etc.) can be automatically populated. In some embodiments, this automatic population of fields can depend on the type of external content 460. For example, in a text-based document, TITLE 412 field can be automatically populated with the selected portion of the text. In the screenshot of FIG. 4, TITLE 412 can be automatically populated with the selected portion of text “Curiosity.” In some embodiments, TYPE 410 field of tagging interface can also be automatically populated. In the screenshot of FIG. 4, TYPE 410 can be automatically populated with a type of the selected portion of text, “Ground Travel.” In some other embodiments, the fields of tagging interface 450 can be filled manually by the user or can be selected from a pull-down list of options.

Tagging interface 450 includes options for designating the type of tag. These options include a property tag option 404, an object tag option 406, and a link tag option 408. It will be understood by a skilled person in the art that it is possible to customize tagging interface 450 to modify the various available options. For example, a selection of property tag option 404 could result in tagging interface 450 adding one or more fields for linking an object to the property. For example, the property “Curiosity” could be linked to an object “Robot.” Moreover, a selection of link tag option 408 could result in tagging interface 450 adding one or more fields linking two or more objects or two or more properties.

After the tagging option is selected and the appropriate fields are filled in, a Create Tag button 414 can be selected to create a tag associated with the selected portion of external content 460. In some embodiments, the properties of created tag can be modified after the tag is created. For example, TYPE 410 field can be changed, if desired, from “Ground Travel” to “Air Travel” after the tag is created. In some embodiments, the created tag can be stored in a memory of the electronic device.

After an object tag is created, it can be displayed in a Tagged objects field 418 of tagging interface 450. Tagged objects field 418 can be useful as it can display all of the created object tags associated with external content 460 in one portion of tagging interface 450. Tagged objects field 418 can also be useful as it can enable a user to modify any of the created tags. Moreover, after property tag option 404 is selected, tagged objects field 418 of tagging interface 450 allows a user to select an appropriate tagged object from tagged objects field 418 for linking that property tag to a tagged object. Further, after a link tag option 408 is selected, tagged objects field 418 of tagging interface 450 could allow a user to select two or more appropriate tagged objects from the tagged objects field 418. Moreover, tagging interface 450 could provide a tagged properties field (not shown) that would provide a user with the option of linking two or more tagged properties.

Tagging interface 450 can also include, in some embodiments, a search for object field 416, which can be used to search for already existing created tag objects in internal database system (e.g., Database System 100). For example, FIG. 4 depicts “Search for object” 416, which is populated with the tag “Curiosity.” If a created tag object is already associated with “Curiosity” in the internal database system, results associated with the existing created tag objects can be displayed in “Search for object” field 416. If such results indeed exist, tagging interface 450 alone or in combination with internal database system 100 can sync the tagged object from tagging interface 450 with the object existing in internal database system 100. In some embodiments, tagging interface 450, using “Search for object” field 416, allows the ability to create links between tagged objects and/or properties from external content with objects and/or properties in internal database system 100. In some embodiments, “Search for object” field 416 provides the ability to create object types and/or property types for entities that exist in internal database system 100. In some embodiments, a user of electronic device 310 is logged in to database system 100 in order to perform the syncing operation.

Created tags and external content 460 can be gathered for storage using, for example, an application program interface (API), such as a Java client API. The API can create one or more parameter-value pairs associated with the tag. For example, with reference to the exemplary embodiments of FIG. 4, the parameter-value pairs that are created could be TagOption:Object, Title:Curiosity, Type:Ground Travel, Content:<label for external content 460>, DateAdded:2012/08/20, User:John Doe, etc. Moreover, external content 460 can be stored in a cache or a directory associated with the tagging interface under a label for that external content 460. By way of example, external content 460 can be stored as external content (as depicted in FIG. 4), a representation of external content 460, alphanumeric characters of external content 460, and/or any audio/visual data of external content 460.

Created tags and external content 460 can be exported to an internal database system (e.g., Database System 100) by selecting an export button 420 (such as the “Export to Palantir” button in FIG. 4) of Tagging Interface 450. In some embodiments, electronic device 310 must be logged into internal database system 100 to export the content 460 and any created tags. In some embodiments, content and created tags can be stored in the external system (e.g., memory of electronic device 310 or a cache associated with a web browser), in internal database system 100, or any combination thereof. In embodiments where the content and created tags are stored in the external system, the content and created tags can be exported after electronic device 310 connects to internal database system 100. In some embodiments, the selection of create tag button 414 causes tagging interface 450 to automatically export the content and created one or more tags to internal database system 100. In some embodiments, electronic device 310 can include an interface for converting the stored parameter-value pairs and the stored content into data compatible with internal database system 100. Alternatively, or additionally, in some embodiments, internal database system 100 includes the interface.

After receiving external content and the created one or more tags, internal database system 100 stores the exported data into appropriate components. For example, external content 460 (or a converted format of external content 460) can be stored in data sources 130, while the parameter-value pairs that were created by electronic device 310 (or a converted format of the parameter value-pairs) can be stored in database 170 according to ontology 150 and object model 160

FIG. 5 is a flowchart representing an exemplary method 500 performed by an electronic device for tagging external content. While the flowchart discloses the following steps in a particular order, it will be appreciated that at least some of the steps can be moved, modified, or deleted where appropriate, consistent with the teachings of the present disclosure.

In this exemplary embodiment, a user can utilize an electronic device (e.g., electronic device 310) that comprises a web browser like, for example, Google™ Chrome™, Mozilla™ Firefox™, Microsoft™ Internet Explorer™, etc. The user can run a web browser to access content external to an internal database system (e.g., database system 100) that is present on a website or otherwise accessible via a network (e.g., network 320), such as the Internet or an intranet. In this disclosure, intranet can mean any network that is understood as a network that does not encompass the Internet including, for example, a local area network, a wide area network, a campus area network, a metropolitan area network, an extranet, a private extranet, any set of two or more coupled electronic devices, or a combination of any of these or other appropriate networks. Also, for the exemplary embodiment of FIG. 5, it is understood that the electronic device is external to an internal database system, as described in relation to FIGS. 1 and 2 earlier, where the database system is a part of an internal network.

In step 505, a bookmarklet is installed in the web browser of the electronic device. A bookmarklet can be a bookmark that is stored in a web browser and can contain JavaScript™ commands to extend the web browser's functionality. That is, a bookmarklet can be a simple “one-click” tool that can add functionality to the web browser. For example, a bookmarklet can modify the appearance of a web page within the web browser by changing the font size or the background color of the text, and/or extract data from a web page.

In some embodiments, a plug-in, instead of a bookmarklet, can be installed. A plug-in can be implemented as a set of software components that adds specific abilities to a larger software application, like a web browser, to enable customizing the functionality of the software application. For example, a plug-in can be installed in a web browser to enable the web browser to play video.

There are some advantages to using a bookmarklet as opposed to a plug-in. For example, a bookmarklet can be web browser-agnostic. That is, the same code underlying a given bookmarklet can be used to run on any of the web browser such as Google™ Chrome™, Mozilla™ Firefox™, Microsoft™ Internet Explorer™, etc. A plug-in, on the other hand, need not be compatible between various web browsers. A user might choose to install a bookmarklet due to its simplicity and browser-agnostic capability.

In some embodiments, a bookmarklet can be installed, for example, by a process similar to adding a bookmark to the web browser. For example, if the user intends to bookmark a particular website, the user can drag an icon associated with the web address (also known as uniform resource locator) of the website to the bookmark bar of the web browser. Similar to the process of adding a bookmark, the user can drag an object or link associated with a bookmarklet to the bookmark bar of the web browser to install the bookmarklet to the web browser. As known in the art, there are several other ways of adding a bookmarklet, for example, using keyboard shortcuts, importing bookmarklets from other web browsers, manually adding by right-clicking the bookmark bar and selecting adding page, etc.

A plug-in can be installed in the web browser instead of, or in addition to, a bookmarklet. A plug-in can be installed similar to any software application like, for example, the web browser. The user can first download the plug-in from an appropriate web site and then can proceed to install the plug-in. Since a typical plug-in is designed to be compatible to a specific web browser (e.g., Google™ Chrome™, Mozilla™ Firefox™, Microsoft™ Internet Explorer™, etc.), the plug-in can become a part of the web browser automatically after the plug-in is installed.

Referring again to FIG. 5, in step 510, the electronic device accesses the external content using the web browser. In this disclosure, “external content” signifies that the accessed content is external to an internal database system (such as Database System 100). The accessed external content can be found on the Internet or can be part of an intranet of an organization. Additionally, external content can be digital content that is accessible via web browsers of electronic devices. In some embodiments, external content can comprise structured or non-structured data including web pages, documents, email messages, text messages, Adobe™ PDF documents, and other media-based content. The other media-based content can comprise external content based on, for example, audio, video, etc. In some embodiments, accessing external content can comprise, for example, opening a web page or a document in the web browser. In some other embodiments, accessing external content can comprise, for example, modifying or editing external content in the web browser.

In step 515, the web browser is enhanced by providing a tagging interface, such as tagging interface 450. Enhancing the web browser can involve rewriting or modifying at least a portion of the underlying code of the web browser, wherein the web browser can display at least some of the accessed external content. The enhancement can be accomplished by running or activating the installed bookmarklet. In some embodiments, when the installed bookmarklet is activated, the underlying code of the web browser specific to the accessed external content can be modified or altered in order to display a tagging interface in the web browser. For example, when a web page on the Internet is the accessed external content (say, a news web page accessed at <http://www.cnn.com>) and is displayed in the web browser, the activation of the installed bookmarklet can enhance the web browser for displaying a tagging interface (such as tagging interface 450) in the web browser.

In some embodiments, enhancing the web browser can also include enhancing the local copy of the external content being accessed in the web browser. For example, if the accessed external content is a news web page associated with CNN™, as noted above, enhancing the web browser can include modifying or editing the specific content associated with the displayed CNN™'s news web page.

Next, in some embodiments, the user can select or highlight at least a portion of the external content for tagging. For example, the user can select a portion of text of a news web page for tagging that portion of the content. The user can select or highlight a portion of the external content (for example, selecting by using a mouse or touchpad) and can select, using the tagging interface, a type of tag to be created for that selected or highlighted portion. The tagging interface can be a graphical user interface that enables a user to create tags for tagging external content. In some embodiments, the tagging interface can enable a user to create tags of different kinds, for example, an object tag (e.g., object tag option 406), a link tag (e.g., link tag option 408), and a property tag (e.g., property tag option 404). The selecting of various tag options can provide different functionalities and fields, as discussed above. After the user selects an appropriate tag option for the selected portion of the external content, the tagging interface provides the ability to create a tag. For example, the tagging interface can include an option called “Create Tag” (Create Tag 414 of FIG. 4).

In step 520, the created tag that is associated with the enhanced web browser is received by the tagging interface. In some embodiments, one or more created tags can be associated with the enhanced portion of the external content. For example, FIG. 4 shows that the text “Curiosity” 402 was selected from the web page displayed in the web browser of FIG. 4. Also, FIG. 4 depicts tagging interface 450 enabling the creation of an object tag associated with the selected text, “Curiosity.” After the user selects the text “Curiosity,” the user can assign some properties for a tag to-be-created and finishes the process of creating the object tag by selecting the option create tag button 414 of FIG. 4. After the create tag button 414 is selected, a tag associated with the selected text, “Curiosity” is created and received by tagging interface 450.

In step 525, the received tag is stored. The received tag can be stored in an external system (e.g., a memory of the electronic device or a cache associated with web browser), or a combination of both. In step 530, the received tag and the external content can be exported to an internal database system (internal database system 100). In some embodiments, the electronic device must be logged into the internal database system to export the external content and any created tags. In some embodiments, content and created tags can be stored in the electronic device and be later exported after the electronic device connects to the internal database system. In some embodiments, the receipt of a created tag causes an automatic export of the content and created one or more tags to the internal database system. In some embodiments, the receipt of the created tag is stored to the internal database system and export step 530 may not be needed.

According to some embodiments, the operations, techniques, and/or components described herein are implemented by one or more special-purpose computing devices (e.g., electronic device 310). The special-purpose computing devices can be hard-wired to perform the operations, techniques, and/or components described herein, or can include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the operations, techniques and/or components described herein, or can include one or more general purpose hardware processors programmed to perform such features of the present disclosure pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices can also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the technique and other features of the present disclosure. The special-purpose computing devices can be desktop computer systems, portable computer systems, handheld devices, networking devices, or any other device that incorporates hard-wired and/or program logic to implement the techniques and other features of the present disclosure.

The one or more computing devices can be generally controlled and coordinated by operating system software, such as iOS, Android, Blackberry, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, VxWorks, or other compatible operating systems. In other embodiments, the computing device can be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface (“GUI”), among other things.

By way of example, FIG. 6 is a block diagram that illustrates a computer system 600. Computer system 600 includes a bus 602 or other communication mechanism for communicating information, and one or more hardware processors 604, coupled with bus 602 for processing information. One or more hardware processors 604 can be, for example, one or more general purpose microprocessors.

Computer system 600 also includes a main memory 606, such as a random access memory (RAM) or other dynamic storage device, coupled to bus 602 for storing information and instructions to be executed by processor 604. Main memory 606 also can be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 604. Such instructions, when stored in non-transitory storage media accessible to one or more processors 604, render computer system 600 into a special-purpose machine that is customized to perform the operations specified in the instructions.

Computer system 600 further includes a read only memory (ROM) 608 or other static storage device coupled to bus 602 for storing static information and instructions for processor 604. A storage device 610, such as a magnetic disk, optical disk, or USB thumb drive (Rash drive), etc., is provided and coupled to bus 602 for storing information and instructions.

Computer system 600 can be coupled via bus 602 to a display 612, such as a cathode ray tube (CRT), an LCD display, or a touchscreen, for displaying information to a computer user. An input device 614, including alphanumeric and other keys, is coupled to bus 602 for communicating information and command selections to processor 604. Another type of user input device is cursor control 616, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 604 and for controlling cursor movement on display 612. The input device typically has two degrees of freedom in two axes, a first axis (for example, x) and a second axis (for example, y), that allows the device to specify positions in a plane. In some embodiments, the same direction information and command selections as cursor control may be implemented via receiving touches on a touch screen without a cursor.

Computing system 600 can include a user interface module to implement a GUI that may be stored in a mass storage device as executable software codes that are executed by the one or more computing devices. This and other modules may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.

In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, qua, C or C++. A software module can be compiled and linked into an executable program, installed in a dynamic link library, or written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules can be callable from other modules or from themselves, and/or can be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices can be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and can be originally stored in a compressed or installable format that requires installation, decompression, or decryption prior to execution). Such software code can be stored, partially or fully, on a memory device of the executing computing device, for execution by the computing device. Software instructions can be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules can be comprised of connected logic units, such as gates and flip-flops, and/or can be comprised of programmable units, such as programmable gate arrays or processors. The modules or computing device functionality described herein are preferably implemented as software modules, but can be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage.

Computer system 600 can implement the techniques and other features described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 600 to be a special-purpose machine. According to some embodiments, the techniques and other features described herein are performed by computer system 600 in response to one or more processors 604 executing one or more sequences of one or more instructions contained in main memory 606. Such instructions can be read into main memory 606 from another storage medium, such as storage device 610. Execution of the sequences of instructions contained in main memory 606 causes processor 604 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry can be used in place of or in combination with software instructions.

The term “non-transitory media” as used herein refers to any media storing data and/or instructions that cause a machine to operate in a specific fashion. Such non-transitory media can comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 610. Volatile media includes dynamic memory, such as main memory 606. Common forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, and networked versions of the same.

Non-transitory media is distinct from, but can be used in conjunction with, transmission media. Transmission media participates in transferring information between storage media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 602. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.

Various forms of media can be involved in carrying one or more sequences of one or more instructions to processor 604 for execution. For example, the instructions can initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 600 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 602. Bus 602 carries the data to main memory 606, from which processor 604 retrieves and executes the instructions. The instructions received by main memory 606 can optionally be stored on storage device 610 either before or after execution by processor 604.

Computer system 600 also includes a communication interface 618 coupled to bus 602. Communication interface 618 provides a two-way data communication coupling to a network link 620 that is connected to a local network 622. For example, communication interface 618 can be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 618 can be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links can also be implemented. In any such implementation, communication interface 618 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link 620 typically provides data communication through one or more networks to other data devices. For example, network link 620 can provide a connection through local network 622 to a host computer 624 or to data equipment operated by an Internet Service Provider (ISP) 626. ISP 626 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 628. Local network 622 and Internet 628 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 620 and through communication interface 618, which carry the digital data to and from computer system 600, are example forms of transmission media.

Computer system 600 can send messages and receive data, including program code, through the network(s), network link 620 and communication interface 618. In the Internet example, a server 630 might transmit a requested code for an application program through Internet 628, ISP 626, local network 622 and communication interface 618.

The received code can be executed by processor 604 as it is received, and/or stored in storage device 610, or other non-volatile storage for later execution.

In the foregoing specification, embodiments have been described with reference to numerous specific details that can vary from implementation to implementation. Certain adaptations and modifications of the described embodiments can be made. Other embodiments can be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims. It is also intended that the sequence of steps shown in figures are only for illustrative purposes and are not intended to be limited to any particular sequence of steps. As such, those skilled in the art can appreciate that these steps can be performed in a different order while implementing the same method. 

What is claimed:
 1. A system configured to provide a tagging interface for tagging content external to a database system, the system comprising: a display configured to display the external content and the tagging interface; a memory device that stores a set of instructions; and one or more processors that execute the set of instructions to: access the external content using a web browser; tag, with the tagging interface in the web browser, at least a portion of the external content; receive a created tag associated with a tagged portion of the external content; and export the external content and the received tag to the database system.
 2. The system of claim 1, further comprising instructions executable by the one or more processors to cause the one or more processors to: receive a selection of a tag option that corresponds with the portion of the external content.
 3. The system of claim 2, wherein the tag option includes at least one of an object tag option, a property tag option, and a link tag option.
 4. The system of claim 2, wherein the received tag defines the portion of the external content to be an object or a property of an object.
 5. The system of claim 2, wherein the received link tag defines a relationship between at least two entities.
 6. The system of claim 5, wherein an entity of the two entities can be an object or a property.
 7. A method for tagging content external to a database system, the method being performed by one or more processors of an electronic device and comprising: accessing, with the electronic device, the external content using a web browser; tagging, with a tagging interface in the web browser, at least a portion of the external content; receiving a created tag associated with a tagged portion of the external content; and exporting, with the electronic device, the external content and the received tag to the database system.
 8. The method of claim 7, further comprising receiving a selection of a tag option that corresponds with the portion of the external content.
 9. The method of claim 8, wherein the tag option includes at least one of an object tag option, a property tag option, and a link tag option.
 10. The method of claim 8, wherein the received tag defines the portion of the external content to be an object or a property.
 11. The method of claim 8, wherein the received link tag defines a relationship between at least two entities.
 12. The method of claim 11, wherein an entity of the two entities can be an object or a property.
 13. The method of claim 7, wherein the electronic content is at least one of a web page, a document, or an email.
 14. The method of claim 7, wherein the electronic content is at least one of an audio file or a video file.
 15. A non-transitory computer readable medium that stores a set of instructions that are executable by at least one processor of an electronic device to cause the electronic device to perform a method for tagging content external to a database system, the method comprising: accessing the external content using a web browser; tagging, with a tagging interface in the web browser, at least a portion of the external content; receiving a created tag associated with a tagged portion of the external content; and exporting the external content and the received tag to the database system.
 16. The non-transitory computer readable medium of claim 15, further comprising instructions executable by the at least one processor of the electronic device to cause the electronic device to perform: receiving a selection of a tag option that corresponds with the portion of the external content.
 17. The non-transitory computer readable medium of claim 16, wherein the tag option includes at least one of an object tag option, a property tag option, and a link tag option.
 18. The non-transitory computer readable medium of claim 16, wherein the received tag defines the portion of the external content to be an object or a property.
 19. The non-transitory computer readable medium of claim 16, wherein the received link tag defines a relationship between at least two entities.
 20. The non-transitory computer readable medium of claim 19, wherein an entity of the two entities can be an object or a property. 